home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: mozart.unx.sas.com!sassek
- From: sassek@unx.sas.com (Steve Krueger)
- Subject: Re: Ceck out this bug. What the *** is SASC/6.56 doing?
- Sender: news@unx.sas.com (Noter of Newsworthy Events)
- Message-ID: <sassek.826742736@sas.com>
- Date: Wed, 13 Mar 1996 18:45:36 GMT
- X-Nntp-Posting-Host: wonka.unx.sas.com
- References: <1120.6643T91T406@login.eunet.no> <sassek.826554207@sas.com> <422.6645T351T2154@login.eunet.no>
- Organization: SAS Institute Inc.
-
- patrick.hanevold@login.eunet.no (Patrick Hanevold) writes:
-
-
- >>You are probably running out of stack. With a standard 4k stack,
- >>after the prolog of main(), you only have 640 bytes of stack left.
- >>Apparently not enough for OpenScreenTags(). The program runs
- >>fine with a 20k stack.
-
- >Guess stack check is bugged then. Hmm.. maby it doesnt work on SC's own
- >code.
-
- No, stack checking is working fine. The prolog code for main()
- determines that there is enough stack for main() to run. This
- is correct. OpenScreenTags() is a system routine that does not
- do stack checking. If you run out of stack while inside a
- a system routine, your program cannot detect it.
-
- One way around this kind of problem is to compile with STACKEXT,
- and then set the global variable __STKNEED to 4k or something similar.
- Then your program will get more stack anytime you have less than 4k
- stack available. BTW the default value for __STKNEED is only 400 bytes,
- which is too small for many applications.
-
- sk
-